Virtual serial port and protocol for use in serial-over-lan communication

ABSTRACT

A method and system of conveying data to a remote computer, which may act as a management console. A virtual communications port is provided to a central processing unit. The virtual communications port is provided using a device distinct from the central processing unit, such as a network controller card with manageability features inborn. The device providing the virtual communications port receives the data written to the virtual communications port. Thereafter, the device transmits the data into a network, addressed for reception by the remote computer. The remote computer may be used as a management console so that keystrokes entered thereupon may be relayed through the virtual communications port to the aforementioned central processing unit.

TECHNICAL FIELD

Embodiments of the present invention relate to computing systems that may utilize serial-over-LAN communication schemes, and more particularly to computing systems that may utilize a serial-over-LAN communication scheme with a virtual serial port and a protocol tailored for such an application.

BACKGROUND

Oftentimes, it is the case that when a computing system requires a diagnostic or maintenance procedure, keystrokes must be entered into the computing system. For example, to update a setting in the basic input/output system (BIOS) of a computing system, a user must typically be present at the system to enter keystrokes into the BIOS screens. Of course, other sorts of diagnostic or maintenance procedures require the same form of keystroke input.

In the context of a large network of computers, such as in a workplace environment with many offices, it may be cumbersome and expensive to generate even simple keystroke input to a computing system. In such circumstances, information technology (IT) professionals may physically travel to the computer in need of diagnostics or maintenance in order to use its keyboard and monitor. This option is time consuming, and may be expensive. Alternatively, an IT professional may attempt to telephonically direct a computer user who is physically in the presence of the computer, so that the computer user can enter the keystrokes using the computer's keyboard. Again, this option may be error-prone and time consuming.

To address the aforementioned issue, some computing systems allow for text-mode screen data to be redirected to a serial port, and allow for keystroke data to be redirected from the serial port. FIG. 1 depicts such a computing system 100. The computing system 100 includes a central processing unit (CPU) 102, which redirects data (such as text-mode screen data) through a universal asynchronous receiver/transmitter (UART) 104 to a baseboard management controller 106. A baseboard management controller 106 is a system that controls environmental variables of the computing system 100 (e.g., monitors and controls the temperature of the computing system 100). The baseboard management controller 106 includes a microcontroller 108, which is coupled to another UART 110. Thus, the CPU 102 may redirect data through the UART 104, which serializes the data, which travels through a switch 112 (further discussion of the switch 112 follows) that directs the data through another UART 110. The second UART 110 deserializes the data, and communicates the data to the microcontroller 108 on the baseboard management controller 106. Thus, the microcontroller 108 may communicate text-mode screen data to a local area network (LAN) 114 via a network interface card (NIC) 116. In reverse fashion, keystroke data may be received via the LAN 114, and redirected to the CPU 102 via the UARTs 104 and 110.

The switch 112 may direct data from the CPU 102 to either the microcontroller 108 on the baseboard management controller 106 or to a serial communications port connector (COM port connector) 118. The COM port connector 118 is a physical arrangement of pins (such as a DB-9 or DB-25 connector, used with an RS-232 serial port) usually accessible from the exterior of the computing system 100. The state of the switch 112 is under the control of the microcontroller 108. When the switch 112 provides connectivity to the COM port 118, the COM port 118 may be utilized as any ordinary COM port 118 would otherwise be used. When the switch 112 provides connectivity to the microcontroller 108 (via the UART 110), the COM port is unavailable for use. Therefore, the COM port 118 is unavailable for use when the CPU 102 is redirecting text-mode screen data or keystroke data through the baseboard management controller 106.

The aforementioned scheme exhibits certain shortcomings. The inclusion of the switch 112 adds complexity and cost for the design of the baseboard management controller 106. Moreover, the need to manage the state of the switch 112 adds complexity to the software/firmware executed by the microcontroller 108. Additionally, data redirected from the CPU 102 to the microcontroller 108 is limited in data rate by the baud rate supported by the UARTs 104 and 110.

For the foregoing reasons, it is evident that there exists a need for a redirection scheme that addresses one or more of the aforementioned shortcomings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a prior-art computing system that can redirect text-mode screen data through a UART.

FIG. 2 depicts one embodiment of a computing system that can redirect data via an integrated multifunction device.

FIG. 3 depicts one embodiment of an integrated multifunction device with a set of virtual COM port registers.

FIG. 4 depicts protocol stack that may be executed by the integrated multifunction device.

FIG. 5 depicts a method for provision of a virtual serial port, according to one embodiment of the present invention.

FIG. 6 depicts one possible embodiment of the protocol stack depicted in FIG. 4.

FIG. 7 depicts the joint flow of operation of the session manager and the serial-over-LAN layer.

FIG. 8 depicts one possible embodiment of the general structure of the serial-over-LAN layer.

FIG. 9 depicts one possible embodiment of the operational flow of the connected state depicted in FIG. 7.

DETAILED DESCRIPTION

FIG. 2 depicts one example of a computing system 200 that redirects text-mode screen data and keystroke data without making use of a switch. The computing system 200 includes a CPU 202, which is coupled to a memory control hub 204. The memory control hub 204 is an arrangement of circuitry that manages and controls access to the system memory 206, graphics card 208, and the input/output (I/O) control hub 210. The I/O control hub 210, in turn, manages and controls access to a flash memory device 212, which stores the basic input/output system (BIOS). It also manages and controls access to a UART 214, which may be embodied as a part of the I/O control hub 210, and manages and controls access to an I/O bus 216, such as a peripheral component interconnect (PCI) bus. (The I/O control hub 210 may also manage and control access to audio channels, USB ports, and other I/O devices that are known in the art, but are not important in the context of this disclosure, and are not depicted herein).

Coupled to the I/O bus 216 is an integrated multifunction device 218. As discussed in more detail below, an integrated multifunction device is a single device that provides more than one function. In the particular example depicted in FIG. 2, the integrated multifunction device 218 is a single device that offers a COM port (i.e., serial port) function and a LAN controller function. Such an integrated multifunction device 218 may be presented in the marketplace as a LAN controller with built-in manageability features.

The integrated multifunction device 218 may include a microcontroller 220 coupled to a UART 222 and a LAN controller 224. Alternatively, the UART 222 circuitry may be physically absent, and present in a virtual sense only, as discussed below. The UART function includes a set of twelve registers (not depicted in FIG. 2) that are accessible by the CPU 202. The registers serve as an vehicle for interacting with the COM port function and software running on the CPU 202. In other words, data is read from and written to the COM port function by reading from and writing to one of the twelve registers. Further, the behavior of the COM port function is controlled by writing to and reading from the remaining seven registers.

Notably, in one embodiment, the integrated multifunction device 218 does not actually contain a UART or a COM port. Rather, the integrated multifunction device 218 contains a set of twelve registers that appear, from the vantage of the CPU 202, to be COM port registers of an ordinary COM port. Firmware or software running on the microcontroller 220 controls the registers in a manner so as to mimic the behavior of a COM port with a device coupled thereto, although no such COM port or device is actually present. Such an arrangement of registers and firmware or software may be referred to as a “virtual COM port” herein. In this way, software running on the CPU 202 may be structured so as to interface with the registers as though they were a vehicle to interact with an actual COM port, although no physical COM port exists.

FIG. 3 depicts the integrated multifunction device 218 in greater detail, including a virtual COM port registers 300. The microcontroller 220 residing on the integrated multifunction device 218 is coupled to the virtual COM port registers 300, which may include twelve registers, accessible through eight I/O addresses. The registers are: the transmit/hold register (THR), the interrupt enable register (IER), the interrupt identification register (IIR), the line control register (LCR), the modem control register (MCR), the line status register (LSR), the modem status register (MSR), a reserved register (RSV), a receiver buffer register (RBR), a FIFO control register (FCR), a divisor latch register—least significant byte (DLL), and a divisor latch register—most significant byte (DLM). Other implementations of COM ports may possess a greater or lesser number of registers, having different functions. Such implementations are within the scope of this disclosure.

Each of the aforementioned registers is typically assigned a particular function in the context of an ordinary COM port. Briefly, their functions are as follows. The transmit/hold register (THR) is generally used to store an outgoing data byte, and is write-only. The receiver buffer register (RBR) contains an incoming data byte, and is read-only. The THR and RBR registers share an I/O address. An attempt to read from the shared I/O address results in a read from the RBR register; an attempt to write thereto results in a write to the THR register.

The interrupt enable register (IER) is generally used to enable and disable interrupts that may be generated during use of the associated COM port.

The interrupt identification register (IIR) is generally used to identify the source of a given interrupt, and is read-only. The FIFO control register (FCR) controls internal FIFO operation in the UART, and is write-only. The IIR and FCR registers share an I/O address. An attempt to read from the shared I/O address results in a read from the IIR register; an attempt to write thereto results in a write to the FCR register.

The line control register (LCR) is generally used to store the communication parameter settings (parity, number of stop bits, etc.). The eighth bit of the line control register is termed the divisor latch bit (DLAB bit). When the DLAB bit is asserted, a write or read command to THR and IER registers results in a write or read to or from the DLL and DLM registers, respectively.

The time base of the UART may be divided, to allow for applications that demand slower speed. A divisor (least significant byte and most significant byte) may be entered in the DLL and DLM registers, when the DLAB bit in the LCR is asserted. The rate of the time base is divided by the divisor entered in these registers, thereby slowing the communication speed of the UART.

The modem control register (MCR) is used to send certain control signals (e.g., this register may be used to set the RTS control signal when the host CPU wants to signal the modem that it wants to send data, or this register may be used to put the port into a loop-back mode in which data that is to be transmitted is returned are received data, as well).

The line status register (LSR) is used to indicate events that may occur on the data line (e.g., received data is ready, received data corrupted by parity error, etc.).

Finally, the modem status register (MSR) is used to store various modem status indicators (e.g., an indication of a ring, an indication that the data set is ready, and indication known as clear to send, which means that the modem is ready to receive input from the PC, etc.).

As stated above, the microcontroller 220 executes firmware or software stored in a memory device 221, which causes the microcontroller to read from and write to the registers 300 as though an actual UART were present. (The memory device 221 is one example of a computer-readable medium upon which the methods disclosed herein may be stored. Other examples include magnetic or optical storage media.) Below is an example of how a real device uses the registers when a real UART is present, followed by an example describing a virtual serial port using the registers 300 in a parallel manner. The examples are intended to provide a flavor of the manner in which the microcontroller 220 can read from and write to the registers 300 to emulate the behavior of an actual COM port.

An ordinary set of COM port registers is coupled to UART. A CPU writes data to be communicated through the COM port to the transmit/hold register (mentioned above). In response, the UART generally enters the data into an internal first-in-first-out (FIFO) buffer. Thereafter, the data is removed from the FIFO buffer and transmitted, one bit at a time (i.e., the data is serialized) through a connector (such as a DB-9 connector), along a serial port transmission line, whereupon the data is received by a device (e.g., a modem) coupled to the other end of the transmission line. If the device coupled to the COM port becomes busy, it may drop the clear to send bit in the modem status register (mentioned above). This generally signals the application utilizing the COM port to stop sending data to the device. As discussed below, a virtual COM port may behave in an identical manner—in this regard and in every other regard, too.

Returning to FIG. 3, therein is depicted a virtual serial port. By this, it is meant that although serial port registers 300 exist, there exists no UART or connector associated with the registers 300. From the vantage of the CPU (not depicted), however, it is not apparent that no actual UART or connector exists. The microcontroller 220 reads from and writes to the registers 300 in a manner mimicking that of a UART with a device coupled thereto. Thus, for example, when the CPU (not depicted) writes data to the virtual COM port, it does so by writing to the transmit/hold register (THR)—the same way it writes data to an ordinary COM port. The microcontroller 220 responds by reading the data written to the transmit/hold register (THR) and communicating the data, through the LAN controller 224, and ultimately to a network 226. If the microcontroller 220 becomes busy, the microcontroller 220 may drop the clear to send bit in the modem status register (MSR), thereby signaling the CPU to desist sending data to the set of COM port registers, a mimicry of the behavior of a device coupled to a COM port. In short, the behavior of the virtual COM port registers 300, as seen from the vantage of the CPU (such as CPU 202, FIG. 2) is identical to that of an ordinary set of COM port registers.

Returning to FIG. 2 and a discussion of the structure of the integrated multifunction device 218, the integrated multifunction device 218 may also include a LAN controller 224. The LAN controller 224 includes a set of registers through which the CPU 202 interacts with the LAN controller 224 functionality. Of course, the LAN controller 224 also includes circuitry to perform low-level functionality including interfacing with the physical communication medium. The integrated multifunction device 218 may embodied as a single chip, or may be embodied as multiple chips that cooperate with one another.

The system 200 depicted in FIG. 2 makes use of the fact that some commercially available BIOSs and operating systems include an option to redirect text-mode screen data to a COM port, and to receive data from the COM port and treat it as incoming keyboard data. By making a selection in such a BIOS or operating system, the CPU 202 may either write text-mode screen data to a COM port, instead of to the screen, or may write text-mode screen data to both the screen and to a COM port. Similarly, data may be read from the COM port and treated as locally-generated keystroke data. By supplying a computing system with a virtual COM port through which access to a LAN may be obtained, serial data may be redirected through the LAN to another computer system.

If the integrated multifunction device 218 is a PCI compatible device, then the virtual serial port may be made available to a CPU by providing a configuration space that announces the presence of a serial port function in a device. For example, such a PCI compatible device includes a PCI configuration space 302, which is a set of registers including a class code register 304 and a base address register (BAR) 306. The class code register 304 contains a value identifying the sort of function provided by the device. Thus, in the context of a device providing a virtual serial port (or an ordinary serial port), the class code register 304 contains a value identifying a serial port function. The base address register 306 is provided in the configuration space 302 so that the BIOS may store therein an I/O address pointing to the COM port registers 300. During startup, the BIOS traverses each I/O bus (such as PCI bus 216) and seeks out each device. Each device found is enumerated. Furthermore, the BIOS seeks out each function offered by each device. Each function of each device is also enumerated. During this process, the BIOS stores an I/O address in the base address register of the configuration space associated with each function of each device. Based on the I/O address stored in the base address register, the BIOS and operating system can determine how to address a particular function on a particular device.

The integrated multifunction device 218 may execute a protocol stack 400, such as the one shown in FIG. 4. In FIG. 4, a given layer depicted therein provides services to layers located above it. As can be seen, the stack 400 includes a network layer 402. In one embodiment, the network layer 402 includes software/firmware providing internet protocol (IP) functionality. The IP functionality provided by the network layer 402 is made available to the transmission control layer 404. According to one embodiment, the transmission control layer 404 includes software/firmware that provides transmission control protocol (TCP) functionality. According to another embodiment, the transmission control layer 404 is software/firmware that provides user datagram protocol (UDP) functionality. The TCP or UDP functionality provided by the transmission control layer is provided to the security layer 406. The security layer 406 is an optional layer that may be wholly absent, may be activated or deactivated, or may be always activated. According to one embodiment, the security layer 406 includes software/firmware that provides transport layer security (TLS) functionality. According to another embodiment, the security layer 406 includes software/firmware that provides security defined by the Intelligent Platform Management Interface (IPMI). The security functionality provided by the security layer 406 is made available to the multiplex layer 408. The multiplex layer 408 is, again, an optional layer. It may be present on a computing system running other forms of redirection (such as IDE redirection, discussed below). The multiplex layer 408 is responsible for determining whether a data message received via the LAN controller 224 should be ultimately redirected to the set of virtual serial port registers or to another set of virtual device registers (such as a set of virtual IDE device registers). The functionality provided by the multiplex layer is made available to a serial-over-LAN layer 410. The serial-over-LAN layer 410 performs many tasks, which are aimed at the goal of receiving data from the set of virtual serial port registers and delivering them to the LAN controller, and vice versa. The serial-over-LAN 410 layer is discussed in greater detail, below.

The software/firmware making up the network layer 402 may be executed by the LAN controller 224 or by the microcontroller 220. The software/firmware making up the other layers 404-410 may be executed by the microcontroller 220 in the integrated multifunction device 218.

In operation, the serial-over-LAN layer 410 receives data from the registers 300, and packages the data therein into commands that are passed downwardly through the protocol stack, destined to be received by a management console (discussed below). As the protocol stack is executed, the commands are packetized and ultimately transmitted through the network, eventually being received by the aforementioned management console.

The management console (not depicted) is a computer system that communicates with the managed computing system 200 (FIG. 2). The management console runs an identical protocol stack (such as 400), so that it can properly interpret the commands received from the managed computing system 200. Consequently, IT personnel at the management console are able to view text-mode screen data redirected from the managed computing system 200. Further, IT personnel can enter keyboard data at the management console, and the management console communicates the data through the network to the managed computing system 200, whereupon it is received by the integrated multifunction device, and is unpacked (by the serial-over-LAN 410 layer) into the virtual COM port registers 300. The BIOS or operating system being executed by the CPU 202 of the managed computing system 200 then receives the data from the virtual serial port registers 300 and treats the data as incoming keystroke data. In this way, remote IT personnel located at the management console are able to diagnose problems and reconfigure the managed computing system 200 without having to be physically present at the system. The management console can also send flow control signals (this is discussed in more detail, below), such as data carrier detected (DCD), data set ready (DSR), ring indicated (RI), etc.

As shown in FIG. 5, a managed computing system (such as computing system 200) executes the following acts. First, as depicted by operation 500, a set of registers dimensioned in size and number to mimic that of a set of serial port registers are presented to the BIOS and/or operating system executed by a CPU as an ordinary set of serial port registers. In the context of performing that task with a PCI device, this includes providing a PCI configuration space having a class code register that identifies the device as having a COM port function, and further having a base address register that can be programmed to point at the aforementioned set of registers. Next, as shown in operation 502, a microcontroller coupled to the aforementioned set of registers is programmed to read and write data to and from the registers in a manner mimicking the behavior of an ordinary COM port with a device coupled thereto. In the context of a serial-over-LAN use, this may include providing a serial-over-LAN application layer, as shown in FIG. 4, and as is discussed in greater detail, below. Finally, as shown depicted by operation 504, data read from the aforementioned set of registers is communicated to a LAN controller (or network interface chip) for communication through a network to a management console or other computing system. Of course, data received from the management console via the LAN controller is unpacked into the aforementioned registers for retrieval by the CPU. Operation 504 may include execution of a protocol stack, such as that shown in layers 402-408 in FIG. 4.

FIG. 6 depicts one possible embodiment of the protocol stack 400 depicted in FIG. 4. As shown in FIG. 6, the serial-over-LAN layer 410 shown in FIG. 4 may be controlled by a session manager 600. Briefly, the session manager 600 is responsible for opening a redirection session (such as a serial-over-LAN redirection session), and is responsible for ensuring that fewer than some maximum number of such sessions are open (example: limit the number of simultaneous serial-over-LAN sessions to only a single such session). The operation of the session manager 600 is discussed in more detail, below.

As can also be seen from FIG. 6, a redirection session other than serial-over-LAN may also be supported by the multifunction integrated device 218. For example, the integrated multifunction device 218 may also provide a set of registers dimensioned in size and number to be identical to that of a set of integrated drive electronics (IDE) device registers. In other words, a virtual IDE device may be provided by the integrated multifunction device 218. The microcontroller 220 in the integrated multifunction device 218 may be programmed to cooperate with a remote management console, so that the microcontroller 218 reads from and writes to the set of registers in a manner mimicking the behavior of an ordinary IDE device. Such functionality is provided by the redirection layer 602, which provides redirection functionality other than serial-over-LAN redirection.

FIG. 7 depicts the joint flow of operation of the session manager 600 and the serial-over-LAN layer 410. As shown in FIG. 7, the session manager 600 may be initially set in motion by the reception of a StartRedirectionSession command from management console. (Of course, commands from the management console are received by way of the LAN controller 224 in the integrated multifunction device 218). The StartRedirectionSession command is the first command that the management console generally sends to the computing system 200 under management. Basically, this command identifies what kind of redirection session should be started (i.e., should a serial-over-LAN session be started, or should another form of redirection session, such as an IDE redirection session, be started). Thus, the StartRedirectionSession command may include at least one argument, in order to fulfill its role of identifying the sort of redirection session to be started.

The StartRedirectionSession command is received by the session manager 600, which causes the session manager 600 to transition to the starting state 700. During the starting state 700, the session manager 600 determines whether opening the requested redirection session would result in more than a maximum number of permitted sessions to be opened. If so, the session manager 600 does not open the requested redirection session. On the other hand, if opening the requested session would not result in more than a maximum number of permitted sessions, the session manager 600 continues forward in its procedure to open a session. Either way, the session manager 600 replies to the management console by sending a StartRedirectionSessionReply message. This message indicates whether the maximum number of redirection sessions is already open, and also indicates whether the particular variety of redirection session requested by the management console is supported by the computing system under management 200.

The session manager 600 remains in the starting state 700 until it receives an AuthenticateSession command from the management console, whereupon it transitions to the authenticating state 702. The AuthenticateSession command identifies a process by which the management console may identify itself, so that the managed computing system 200 can verify that the console indeed has the authority to start the redirection session. For example, the AuthenticateSession command may include arguments such as a user name and password, for the aforementioned purpose. If the authentication fails (e.g., the username or password provided by the management console is incorrect), then the session manager 600 remains in the authenticating state 702, awaiting an AuthenticateSession command with a correct username and password. An AuthenticateSessionReply message is returned to the management console indicating that the authentication failed. On the other hand, if the authentication is successful, an AuthenticateSessionReply message is returned to the management console indicating the success, and the serial-over-LAN layer 410 transitions to the starting serial-over-LAN (SOL) state 704.

In the starting SOL state 704, the serial-over-LAN layer 410 awaits a StartSOLRedirection command from the management console. The StartSOLRedirection command tells the serial-over-LAN layer 410 that it should start forwarding serial-over-LAN messages to the management console. In other words, it marks the beginning of the serial-over-LAN session. The SartSOLRedirection command may contain certain arguments that configure the serial-over-LAN layer 410. FIG. 8 depicts the general structure of the serial-over-LAN layer 410. Briefly, the serial-over-LAN layer 410 includes a transmission buffer 800 and a reception buffer 802. The serial-over-LAN layer 410 may also include four clocks: (1) a transmission buffer timer 804; (2) a reception buffer timer 806; (3) a heartbeat timer 808; and (3) a session timeout timer 810.

During operation, redirected data from the CPU 202 is received from the COM port registers 801 (which may be a set of virtual COM port registers, as shown in FIG. 3), and stored in the transmission buffer 800. The transmission buffer 800 may be a FIFO buffer. As discussed in more detail below, upon the occurrence of certain events, data is removed from the transmission buffer 800, packaged into commands, and communicated to the multiplex layer 408 for communication to the management console. The length of the transmission buffer 800 may be determined by an argument of the StartSOLRedirection command.

Commands from the management console are received from the multiplex layer 408 and are placed into a reception buffer 802. Like the transmission buffer 800, the reception buffer 802 may be a FIFO buffer. As discussed in more detail below, upon the occurrence of certain events, commands are removed from the reception buffer 802 and unpacked into the COM port registers 801. Such commands may contain data bytes to be conveyed to the host CPU 202 via the RBR register, or may contain control signals conveyed via the MSR register.

The serial-over-LAN layer 410 includes a transmission buffer timer 804. When the transmission buffer timer 804 expires, data in the transmission buffer 800 is removed and packaged into commands that are communicated to the multiplex layer 808. The StartSOLRedirection command may configure the transmission buffer timer 804 to expire after a selected period of time (e.g., the StartSOLRedirection command may configure the transmission buffer 804 to expire after 10 ms or 20 ms). Data is also removed from the transmission buffer 800 when the buffer 800 becomes full. Each time the transmission buffer 800 is emptied, the transmission buffer timer 804 is reset.

As mentioned above, the serial-over-LAN layer 410 also includes a reception buffer 802. When the reception buffer timer 806 elapses, data bytes in the reception buffer 802 are dropped, because the host appears to be too slow to read the data. The StartSOLRedirection command may configure the reception buffer timer 806 to elapse after a selected period of time. Data is also removed from the reception buffer 802 when the buffer 802 becomes full. Each time the reception buffer 802 is emptied, the reception buffer timer 806 is reset.

The StartSOLRedirection command may also configure the heartbeat timer 808 to expire after a chosen period of time. Upon expiration of the heartbeat timer 808, a heartbeat message is communicated to the management console to indicate that the serial-over-LAN session is still active. The heartbeat timer 808 is reset every time a heartbeat message is sent or any other message/command is sent to the management console.

The StartSOLRedirection command may also configure the session timeout timer 810 to expire after a chosen period of time. Upon expiration of the session timeout timer 810, the serial-over-LAN session is terminated, as it is inferred that the management console is no longer in communication with the computing system under management 200 for one reason or another. The session timeout timer 810 is reset every time a message is received from the management console.

The StartSOLRedirection command may also set an initial value for a console sequence number. Each subsequent message from the management console includes a console sequence number, with each successive message containing a sequence number that has been incremented by one. The console sequence number ensures that its messages are received and acted upon in the correct order at the managed computing system 200.

Upon reception of the StartSOLRedirection command, the serial-over-LAN layer 410 transitions from the starting SOL state 704 to the connected state 706. To indicate that such a transition has been made, a StartSOLRedirectionReply message is sent to the management console. The StartSOLRedirectionReply message informs the management console that the serial-over-LAN session has started. Additionally, it may indicate the size of the reception buffer 802. The management console should not send data in blocks larger than the size of the reception buffer 802, because the serial-over-LAN layer 410 would not be able to enter such a block of data into the buffer 802.

Although the state transition flow depicted in FIG. 7 describes the management console initiating a serial-over-LAN session, a managed system 200 may also initiate a session. In such a scenario, the managed system 200 may transmit the StartRedirectionSession and StartSOLRedirection commands to the management console, instead of the management console transmitting such commands to the managed system 200.

During the tenure of the connected state 706, the serial-over-LAN layer 410 awaits the occurrence of certain events. In response to these events, the serial-over-LAN layer 410 reacts as depicted in FIG. 9.

As discussed briefly above, whenever the transmission buffer 800 becomes full, or whenever the transmission buffer timer 804 elapses, the connected state 706 transitions from an awaiting event operation 900 to a send DataFromHost message operation 902. During this operation 902, a DataFromHost message is sent from the serial-over-LAN layer 410 to the multiplex layer 408, for ultimate delivery to the management console. The DataFromHost message communicates the data retrieved from the transmission buffer 800 to the management console, using a message type identifier to identify the block of data as being redirected data (such as redirected text-mode screen data), as opposed to some other type of data, such as control data from the COM port registers 801. After sending the DataFromHost message to the multiplex layer 408, the connected state 706 returns to the awaiting event operation 900.

As shown in FIG. 9, the management console may transmit a KeepAlivePing message. The management console may send such a message to the managed computing system 200 when a given period of time has passed without either receiving a message from the system 200 or sending a message to the system 200. In response to reception of a KeepAlivePing message, the connected state 706 transitions from the awaiting event operation 900 to the send KeepAlivePong message operation 904. During this operation 904, a KeepAlivePong message is returned to the management console (by way of the multiplex layer 408). After transmission of the KeepAlivePong message, the connected state returns to the awaiting event operation 900. By virtue of this “ping” and “pong” exchange, the management console can verify that the serial-over-LAN session is still active. If, after transmission of a KeepAlivePing message, a given period of time elapses without the management console receiving a KeepAlivePong message, the management console closes the serial-over-LAN session, based on the assumption that the session is no longer active for one reason or another.

As is also shown in FIG. 9, upon the heartbeat timer 808 elapsing, the connected state 706 transitions from the awaiting event operation 900 to the send heartbeat message operation 906. This message serves a similar purpose to that of the KeepAlivePong, i.e., it confirms to the management console that the redirection session is still valid. Upon transmission of heartbeat message, the connected state returns to the awaiting even operation 900.

When a COM port control line changes state, the connected state 706 transitions from the awaiting event operation 900 to the send ControlsFromHost message operation 908. During this operation 908, a ControlsFromHost message is sent to the management console. The ControlsFromHost message includes a message type identifier that indicates that the message is delivering control data (as opposed to text-mode screen data). The control data follows the message type identifier. By forwarding control data to the management console, the management console may be informed of standard COM port status information (e.g., the request to send (RTS) line in the COM port is asserted or deasserted, indicating that the CPU is not ready to transmit data, or the data terminal ready (DTR) line in the COM port is asserted or deasserted, indicating either that the CPU 202 is or is not ready to communicate).

When redirected keystroke data is received from the management console, it is embedded within a DataToHost message. Upon reception of such a message, the connected state transitions from the awaiting event operation 900 to a pass upstream operation 910. During this operation 910, the DataToHost message is unpacked, meaning that the keystroke data embedded therein is extracted and placed into the proper register within the set of COM port registers 801 for communication to the CPU 202. Alternatively, the data may also be placed into the reception buffer 802, if such an option is enabled. Upon completion of operation 910, the connected state reverts to the awaiting event operation 900.

When COM port control data is received from the management console, it is embedded within a ControlsToHost message. Upon reception of such a message, the connected state transitions from the awaiting event operation 900 to a pass upstream operation 912, as shown in FIG. 9. During this operation 912, the ControlsToHost message is unpacked, meaning that the COM port control data embedded therein is extracted and placed into the proper register (modem status register—MSR) within the set of COM port registers 801 for communication to the CPU 202. Upon completion of operation 912, the connected state reverts to the awaiting event operation 900.

As mentioned above briefly, the serial-over-LAN layer 410 includes a session timeout timer 810. The session timeout timer 810 is reset every time a message is received from the management console. Should the session timeout timer 810 expire, the serial-over-LAN layer 410 transitions to the socket invalid state 710 (see FIG. 7), as shown by operation 914. The session timeout timer 810 allows the managed computing system 200 to infer that the redirection session has been compromised in some fashion (e.g., the communication link has been lost, or the management console has crashed, etc.), and to respond by invalidating the redirection session.

When finally the IT professional at the management console has completed his or her remote diagnosis or configuration work upon the managed computing system 200, he may close the redirection session. The management console commands the closing of the redirection session by sending an EndSOLRedirection command, as shown in FIG. 7. The EndSOLRedirection command is received by the serial-over-LAN layer 410, and informs the layer 410 that the redirection session has ended, meaning that the layer 410 should cease forwarding any messages to the management console. Reception of the EndSOLRedirection command causes the serial-over-LAN layer 410 to transition to the closing state 708. Upon transition into the closing state 708, the serial-over-LAN layer 410 transmits an EndSOLRedirection message to the management console, which is a message that confirms to the management console that the serial-over-LAN layer 410 has ended the redirection session.

The serial-over-LAN layer remains in the closing state 708 until the reception of an EndRedirectionSession command. The EndRedirectionSession command is received by the session manager 600, and informs the session manager that the redirection session has come to an end. In response, the session manager 600 closes the communication socket that had been utilized by the serial-over-LAN layer 410 during the redirection session. Therefore, the session manager 600 transitions to a socket invalid state 710. Although not depicted, reception of a StartRedirectionSession command causes the session manager 600 to transition from the socket invalid state 710 to the starting state 700, and the aforementioned state flow commences again.

Embodiments of the invention may be implemented in one or a combination of hardware, firmware, and software. Embodiments of the invention may also be implemented as instructions stored on a machine-readable medium (such as memory device 221, shown in FIG. 2), which may be read and executed by at least one processor to perform the operations described herein. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium may include read-only memory (ROM), random-access memory (RAM), magnetic disc storage media, optical storage media, flash-memory devices, electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others.

The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims.

In the foregoing detailed description, various features are occasionally grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment. 

1-33. (canceled)
 34. An apparatus comprising: a controller comprising a microcontroller and a virtual COM port, the controller to: receive a first command to start an identified redirection session, the identified redirection session being selected from a plurality of varieties of redirection sessions, the varieties comprising a serial-over-local area network (LAN) redirection session and another variety of redirection session; determine whether the identified redirection session is permitted; and unless the identified redirection session is determined to be not permitted: start the identified redirection session and continue the identified redirection session until a second command is received.
 35. The apparatus of claim 34, wherein: if a certain number of permitted redirection sessions is already established, the identified redirection session is determined to be not permitted.
 36. The apparatus of claim 34, wherein: the second command comprises at least one of the following: a stop redirecting command to stop redirecting; and a close redirecting command to close the identified redirection session.
 37. The apparatus of claim 34, wherein: the another variety of redirection session comprises an IDE redirection session.
 38. The apparatus of claim 34, wherein: if initiation of the identified redirection session is unauthorized, the identified redirection session is determined to be not permitted.
 39. The apparatus of claim 34, wherein: the controller also is to execute a security protocol to be used in the identified redirection session.
 40. The apparatus of claim 34, wherein: the controller comprises a single chip that includes the microcontroller, the virtual COM port, and a network controller, the network controller to be coupled to a network; and the apparatus also comprises a central processing unit (CPU) coupled to the microcontroller via an input/output (I/O) bus.
 41. The apparatus of claim 34, wherein: the first and second commands are received from a remote computer via a network.
 42. A method comprising: receiving a first command to start an identified redirection session, the identified redirection session being selected from a plurality of varieties of redirection sessions, the varieties comprising a serial-over-local area network (LAN) redirection session and another variety of redirection session; determining by a controller whether the identified redirection session is permitted, the controller comprising a microcontroller and a virtual COM port; and unless the identified redirection session is determined to be not permitted: starting the identified redirection session and continuing the identified redirection session until a second command is received.
 43. The method of claim 42, wherein: if a certain number of permitted redirection sessions is already established, the identified redirection session is determined to be not permitted.
 44. The method of claim 42, wherein: the second command comprises at least one of the following: a stop redirecting command to stop redirecting; and a close redirecting command to close the identified redirection session.
 45. The method of claim 42, wherein: the another variety of redirection session comprises an IDE redirection session.
 46. The method of claim 42, wherein: if initiation of the identified redirection session is unauthorized, the identified redirection session is determined to be not permitted.
 47. The method of claim 42, wherein: the first and second commands are received from a remote computer via a network.
 48. Machine-readable memory storing instructions that when executed by a machine result in operations comprising: receiving a first command to start an identified redirection session, the identified redirection session being selected from a plurality of varieties of redirection sessions, the varieties comprising a serial-over-local area network (LAN) redirection session and another variety of redirection session; determining by a controller whether the identified redirection session is permitted, the controller comprising a microcontroller and a virtual COM port; and unless the identified redirection session is determined to be not permitted: starting the identified redirection session and continuing the identified redirection session until a second command is received.
 49. The memory of claim 48, wherein: if a certain number of permitted redirection sessions is already established, the identified redirection session is determined to be not permitted.
 50. The memory of claim 48, wherein: the second command comprises at least one of the following: a stop redirecting command to stop redirecting; and a close redirecting command to close the identified redirection session.
 51. The memory of claim 48, wherein: the another variety of redirection session comprises an IDE redirection session.
 52. The memory of claim 48, wherein: if initiation of the identified redirection session is unauthorized, the identified redirection session is determined to be not permitted.
 53. The memory of claim 48, wherein: the first and second commands are received from a remote computer via a network. 